Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-89331 | VRAU-PG-000030 | SV-99981r1_rule | Medium |
Description |
---|
Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to configure auditing to do this. DBMSs typically make such information available through views or functions. This requirement addresses explicit requests for privilege/permission/role membership information. It does not refer to the implicit retrieval of privileges/permissions/role memberships that the DBMS continually performs to determine if any and every action on the database is permitted. |
STIG | Date |
---|---|
VMW vRealize Automation 7.x PostgreSQL Security Technical Implementation Guide | 2018-10-12 |
Check Text ( C-89023r1_chk ) |
---|
At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/pgdata/postgresql.conf If "log_statement" is not "all", this is a finding. |
Fix Text (F-96073r1_fix) |
---|
At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET log_statement TO 'all';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();" |